Essential Terms — C09
The Hamilton and Alexandra College · Year 12 · 2026
A glossary of every term you need to recognise and use correctly across C09. Click a term to expand its definition. If you cannot define a term in your own words, you cannot use it with confidence when it counts.
flowchart TD
R["C09 vocabulary<br/>16 terms"]
R --> G0["Beta testing<br/>4 terms"]
R --> G1["Data collection from beta testers<br/>4 terms"]
R --> G2["Reporting results<br/>4 terms"]
R --> G3["Modifications based on feedback<br/>4 terms"]
Where the C09 vocabulary sits, and how much of it is in each group — the 4 sections below follow the same order. Revise the heavy groups first.
Beta testing
Beta testing
The phase of software testing where a sample of the intended audience tests the software in a real environment.
Test scenario
A specific situation or workflow that a beta tester is asked to perform in order to evaluate the functionality, usability or reliability of the software.
Test plan
A document that outlines the objectives, scope, schedule and approach for beta testing, including which features to test and what data to collect.
Personas
Fictional characters created based on user research to represent the different user types that might use a service, application, product, site or brand.
Data collection from beta testers
Data collection
The systematic gathering of feedback, observations and measurements from beta testers during and after testing sessions.
Observation (beta testing)
Watching beta testers interact with the software to identify usability issues, confusion points or unexpected behaviours.
Survey
A structured set of questions given to beta testers to collect quantitative and qualitative feedback about their experience with the software.
Feedback
Information provided by beta testers about their experience, including issues encountered, suggestions for improvement and overall satisfaction.
Reporting results
Bug report
A documented record of an error or defect found during beta testing, typically including steps to reproduce, expected behaviour and actual behaviour.
Reporting results
The process of compiling and presenting beta testing findings, including issues discovered, tester feedback and recommendations for improvement.
Testing table
A commonly used way to record evidence of functionality testing, documenting test cases, expected results and actual results.
Priority (bug classification)
A ranking assigned to an issue found during beta testing that indicates how urgently it needs to be addressed before release.
Modifications based on feedback
Modifications
Changes made to the software based on feedback and issues identified during beta testing, aimed at improving functionality, usability or performance.
Functionality
The range of operations that can be performed by a software system as defined by its requirements.
Usability
The ease with which a user can interact with a software system to achieve their goals efficiently and satisfactorily.
Evaluation criteria
Performance criteria made from the expectations and specification, used to judge whether the software meets its intended purpose.
See also
- C09 home page — everything else for this criterion